Skip to content

Conversation

@jkoritzinsky
Copy link
Member

Enable signing using the Arcade signing infra in VMR scenarios. This does not move the dotnet-runtime-official pipeline to use the Arcade signing infra, similar to how #99432 did not enable -publish in dotnet-runtime-official.

This PR adds the -sign flag to the inner invocation when the outer invocation is invoked with the -sign flag to ensure we go down the Arcade signing and publishing route as expected.

Based on the work in #100004

Fixes #108605

Runtime official build: https://dev.azure.com/dnceng/internal/_build/results?buildId=2561356&view=results

Copy link
Member

@ViktorHofer ViktorHofer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM if it works

@jkoritzinsky
Copy link
Member Author

Signing logs look good for the runtime official build. I'll merge this in so it can flow and catch up with dotnet/sdk#44207, which enables some signing builds in the VMR.

@jkoritzinsky jkoritzinsky merged commit 4bb3219 into dotnet:main Oct 16, 2024
@jkoritzinsky jkoritzinsky deleted the arcade-sign branch October 16, 2024 22:09
@kasperk81
Copy link
Contributor

@jkoritzinsky is this error related: dotnet/sdk#44014 (comment)?

@jkoritzinsky
Copy link
Member Author

That may be. I'll look into it

@jkoritzinsky
Copy link
Member Author

That error should be fixed by #108990

@github-actions github-actions bot locked and limited conversation to collaborators Nov 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Enable arcade -sign functionality in runtime

3 participants